Skip to content

Fix parsing errors on semicolon-delimited generic type parameters in routine implementation headers #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 22, 2024

Conversation

cirras
Copy link
Collaborator

@cirras cirras commented Nov 15, 2024

Previously, only comma-delimited type parameters were parsing correctly.

Fixes #302.

@cirras cirras requested a review from fourls November 15, 2024 00:49
Copy link
Collaborator

@fourls fourls left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a couple of questions about the grammar rule names, that's all. Grammar changes make sense to me and seem to work well.

Specifically, in routine implementation headers.
Previously, only comma-delimited type parameters were parsing correctly.
@cirras cirras force-pushed the semicolon_generic_arguments branch from 2251b13 to 3c85b75 Compare November 22, 2024 03:31
@cirras cirras requested a review from fourls November 22, 2024 04:01
Copy link
Collaborator

@fourls fourls left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@cirras cirras merged commit dd36747 into master Nov 22, 2024
5 checks passed
@cirras cirras deleted the semicolon_generic_arguments branch November 22, 2024 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Parsing error on semicolon-separated generic arguments in routine implementation
2 participants